Customize jpi
task to include api-viewer
#1244
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an alternate potential fix for JENKINS-66988.
It reverts the current fix and updates the
war
task configuration to thejpi
task configuration. jenkinsci/gradle-jpi-plugin@4f4495a (first released in v0.39.0 of the jpi plugin) stopped applying the war plugin in favor of defining ajpi
task that was of typeWar
. This was not previously included in the migration guide for v0.39.0 (jenkinsci/gradle-jpi-plugin#139), but I will add it there now with a reference to this change.I believe this is working as expected. Here is what I did to verify the api-viewer files were included in the generated plugin archive:
Related: